More Pages: Osborne Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39


harmless comic thriller
Needs concentration
QUALITY READING

Fun afternoon readIt doesn't break any new ground or make any brilliant points, but it's a fun read.
Not only read it, but performed it.
Creating the ProtestantsThe scope of the play is too large--it tries to cover too much time rather than concentrating on one (or a few) specific events. But it is a curious and fascinating play; few are written about religion any more, and for that alone it is engrossing.


why oh why do we lie
GREAT BOOK!Read more Magic Tree House books! "High Tide in Hawaii" is coming soon!
Thanksgiving on Thursday

It's OK
Really worth reading

Weak
A book on religions for people age 9-90+

A disappointing end...
Exciting and Worth the Read!

An okay book but not worthy of its price tag
Most accurate and realistic pricing for records

Ok look at the Mekong AreaThe book starts off a little slow but gets much better as it tells the stories of explorers from Europe attempting to navigate the Mekong River. I had never heard of some of these guys and there stories were very interesting.
However, I was surprized that the stories were mostly about Laos and Cambodia and not much was written about Vietnam.
I was also surprized at how light the chapters dealing with the war in IndoChina and their aftermaths were. He never goes into deep detail about anything. What he writes about is interesting but it never gets into anything beyond the surface. I understand this is not a book about the war, but on the otherhand he does not reveal enough of his own experiences to make this fully a travel book.
I feel the book gets muddled again towards the end while discussing the impacts of building dams along the Mekong. The author repeats himself quite a bit at this point. I also felt his conclusions were a little weak, again not really revealing anything
The bottom line on the book is this: it is interesting in parts and is decent enough reading. But I do not recommend dropping everything and reading it. It is not horrible, but at the same time it is not THE book on Southeast Asia.
The History of a river.The river ran through six countries and had seen civilizations emerge and disappear. It had also seen revolution, war, pollution, and destruction. Countries in the upper Mekong liked to dam the river to harness electricity while people in the lower part of the river need its water for agriculture and for its fish. Building dams in the upper Mekong could affect the ecology in the lower Mekong delta. The balance of these antagonistic goals could only be solved if the governments involved were more considerate to each other.
No one could tell the history of the Mekong better than the author.
AVENTURE IN INDOCHINA

Excellent treatment of the EJB 2.0 (PFD 2) spec, and more...Let me start by sharing a secret: since January I have been eagerly awaiting the arrival of the 2nd Ed. of Ed Roman's hugely popular EJB book. Well, guess what: while Ed's book is going through community review at theServerside.com (I applaud Ed for being the first to do this, although it may or may not have slowed down the publication process), Wrox managed to go a leg up and became the first publisher of an EJB 2.0 book. Judging from the content of the current book, I have good reasons to say that it has raised the bar for the next generation of EJB titles coming out in the 2nd half of this year. Why? For one thing this book is based on the new EJB 2.0 spec and is up-to-date with PFD 2. As if this not enough a selling point by itself, Wrox also threw in a bunch of other high-octane topics, which made the total value proposition very compelling.
Let's now go through the content of the book, should we?
Chapters 1 to 4 mostly target EJB newcomers. Here you find short and sweet code samples for each flavor of EJB 1.1 session and entity beans. The author's emphasis is clearly on the client views and life cycles of these beans. Many state and sequence diagrams are used to help readers to come to a good grip of this critical material. I consider the goal superbly achieved, even though the code could have used some System.out.println calls to demo actually how bean classes are invoked by an EJB container. Well, save that as your homework.
Chapters 5 and 6 cover the new EJB 2.0 entity bean features we all have been waiting for, i.e., local interfaces, container-managed relationships, home methods, and EJB QL, among others. Dan O'Connor was at his best again explaining how the new spec solves some of EJB 1.1's toughest problems, like the need to use coarse-grained beans to cut down the number of remote calls. Experienced EJB developers, start here.
Chapter 7 introduces MDB. Frankly, I would like to see it augmented to include more details on transactional MDB. Well, Tyler Jewell should fill that void in Ed's book.
Chapter 8 deals with EJB environment, an often-confusing topic to many. How do I specify a DataSource in my ejb-jar.xml file? What does "java:comp/env/..." mean and where does it come from? You get the answers here.
Chapters 9 and 10 are about EJB transactions and Security. And let me tell you - read these vital topics here and forget about any other book. The discussion is so much better in breadth and depth than anywhere else. You need an example on a distributed TX? No problem. Want to understand security principals? They have it covered.
Chapter 11 starts a section on EJB design issues by providing some well-thought-out advice. The topics are so timely and relevant, like bean granularity, session vs. entity beans, BMP vs. CMP, which people ask on a daily basis at various EJB forums. EJB architect wanna-be's: read this chapter and start to enjoy what used to be sleepless nights.
Chapter 12 is about EJB Design Patterns. Well, I guess you cannot cover in one chapter what 3 Sun J2EE patterns gurus wrote in an entire book. Go buy "Core J2EE Patterns" instead.
Chapter 13 tries to show how to use UML to design EJB's. Frankly, this topic is yet to be mature and I doubt many people really practice such. It is still food for thought though.
Chapter 14: if you read no other chapter in the book, please do read this one. EJB developers live and die on the performance of the beans they write. Bean-test is probably the best-known EJB testing tool today and this chapter shows you how to use it.
Chapter 15 gives you more stuff like patterns, idioms that you can use to achieve optimal EJB performance and scalability. It also explains how EJB containers optimize callbacks. To be honest, things start to get a little bit repetitive but I had no major complaint.
Chapter 16: if you believe in BMP or writing SQL is in your blood, this is the one for you. You see how the dirty flag is used, and how coarse-grained bean modeling parent-child relational tables are written. This is a very useful chapter about handling traditional RDBMS-based relationships in the EJB 1.1 world.
Chapter 17: if you are a black-belt EJB developer and want to try you hand to become an EJB container writer, read this. If you brain is swollen by now, save this chapter for later.
Chapter 18 tries to put together a real-world J2EE sample application with servlets, JSP's and EJB's. Well, I only know one attempt that may have ended with some sort of a deliverable(the end-result is known as the Java Pet Store). FYI that pet project of someone has gone through 3 revisions and people are still tinkering with it.
Chapters 19 to 21 are about interoperating with EJB from COM, CORBA, and WAP clients. They are good enough to get you started by following the examples step-by-step.
Chapter 22 is about J2EE as Web Services. IBM's solution is the main one showcased here. Stay tuned.
The book ends with Appendices A to G, which all evolve around the deployment of a simple EJB app on various commonly found app servers. Take a look if you are starting out with EJB; otherwise join the Java Pet Store deployathon for more fun.
Now you ask me: what's missing from the book? Well, topics like EJB build and packaging strategy will definitely of interest to many. Discussion on clustering is also sorely missed.
Overall, I am excited about the book. I can imagine Ed Roman et al. and Richard Monson-Haefel working hard to top this one. To me, competition is a healthy thing.
Great coverage of EJB's and 2.0In the tradition of Wrox books, it offers good coverage of the entire EJB API. While some topics weren't covered exhaustively, that is not what these books are for. This book does provide *effective* coverage of almost everything in EJB 2.0. There is also coverage of design, which is a nice addition!
It is GREAT for it's intended purpose. Highly recommended...
Great book even for the experienced!Although I have been working with EJB for sometime, the book covers the topics that I don't have time to play around with - it provides very good coverage of topics such as Local interfaces and their uses, EjbQL, and home methods (finally!)
The only chapters 19-21 are the only ones that do not go into real depth - but they shouldn't since they relate to topics not necessarily meant for this book; however, they give a great examples to start from such as the wireless one.
I definitely recommend this book - I already have to the rest of my team!


Has no real feel of Christie!My second complaint was that hardly anything had been done to make this a novel. It felt like a play that had just had the stage directions and blocking taken out of it. More should have been done to have given this novel some novelization.
Third, this was the only Hercule Poirot novel with Captain Hastings in it where Hastings does not narrate the story, so why did the author even bother with Hastings? Hastings also blatantly eavedrops in the story, and in every other book he's ever been in he's always chastising Poirot for doing the same thing, and is embarrassed that Poirot would do such a thing. A most blatant derailing from standard Christie.
My biggest problem was that the story dragged on, seemingly endlessly for such a short book. I had this one pegged early, an unusual circumstance for me in reading a Christie story. Over all, I think Poirot should have been left dead, and this book never written since it did nothing to infuse me with a sense of wonder at his incredible rendering of a murder using his little grey cells.
I give it 3 stars, and still feel I'm too generous.As for the plot (without giving it away), let's just say that the mystery was easy to solve. To say the least, part of the solution had already been used by Agatha Christie in "The Mysterious Affair at Styles." Therefore, the publication of "Black Coffee" as a novel cannot be really justified, since this second-rate Christie material, for the most part, had already been used before in other Christie novels. Making a novel out of "Black Coffee" is useless. It's just the same as if someone wanted to write a novel version of Christie's play "Alibi," when the latter is already based on her novel "The Murder of Roger Ackroyd".
Read this book!p.s. - After blabbing on and on about the wonderful Agatha Christie mysteries to my twelve-year-old cousin (whom I'm very close in relationship to), I've managed to get her hooked on the Agatha Christie novels. Hurray for me! Now I have a close friend to converse over with these wonderful books! We also exchange our Agatha Christie books with each other now, and recommend ones that we've borrowed from the library or another friend. I strongly recommended Black Coffee to her. She, too, has not read any Miss Marple mysteries yet, and is thoroughly interested in Hercule Poirot's cases. Ms. Christie has quite a brilliant mind, and we praise her for that.
Set in Regina, Just For Comfort is a comic thriller involving drugs, crooked cops, dog shootings, infidelity, grouse hunting and taxidermy. Author Ralph Osbourne can write some though, and knows where to start a story: the protagonist is trying to dispose of the assumedly OD'ed body of his bimbo future daughter-in-law. Hijinks ensue, and overall, not bad hijinks and not a bad read.
A few things bother me: our 'hero', Frank, a former bistro owner and currently a marijuana salesman is too capable, too worldly. He comes off as a poor man's James Bond. Apparently his secret agent training comes from being a bird hunter (for the record, the hunting stuff peppered through the book is pretty good and believable)
This first novel looks over its own shoulder a lot. Most of the characters knew each other in their gloried 1970's youth and there are regular winks to their bell-bottomed past; but despite the aging of the characters, wisdom has not been gained, throwaway Lao Tzu quotes notwithstanding. What you have is a collection of middle-aged guys who either haven't grown up yet, or have slided into a born-again adolescence. Most of them have quit smoking cigarettes, so that's something. The women, for the most part, are written as being either manipulators and/or psycho harpies. As far as I can tell, they smoke. Hmm..
As a plot-driven writer, Osbourne is happiest with one or two note characters; a few brief characterizations are sufficient, and then they all act out their roles with few surprises in this twisty little drama.
Just for Comfort is like an evening at the bar with a bunch of mates ' some tall tales, some casual we-are-all-men-here misogyny and enough gonzo danger to make the evening both mildly memorable and totally harmless.